[INFO] fetching crate mockers 0.23.0...
[INFO] fixing mockers-0.23.0 against try#622891a4e29178280638a6b63a8908bde2c0c854+cargoflags=-Zfix-edition=end=2015,2024 for pr-157817-2
[INFO] extracting crate mockers 0.23.0 into /workspace/builds/worker-7-tc2/source
[INFO] started tweaking crates.io crate mockers 0.23.0
[INFO] removed 0 missing tests
[INFO] finished tweaking crates.io crate mockers 0.23.0
[INFO] tweaked toml for crates.io crate mockers 0.23.0 written to /workspace/builds/worker-7-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate mockers 0.23.0 on toolchain 622891a4e29178280638a6b63a8908bde2c0c854
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]      Locking 36 packages to latest compatible versions
[INFO] [stderr]       Adding indoc-impl v0.3.6 (available: v0.3.7)
[INFO] [stderr]       Adding itertools v0.8.2 (available: v0.15.0)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/source:/opt/rustwide/workdir:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:3a6becf2bc8dde7f3fa57ede90e4f284e72d296796fc446bbb1e2c7cc0530151" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] 27636d7642f2e9e2ebab7480526eae27b61d05173667e39b834b645e35f41b71
[INFO] running `Command { std: "docker" "start" "27636d7642f2e9e2ebab7480526eae27b61d05173667e39b834b645e35f41b71", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "27636d7642f2e9e2ebab7480526eae27b61d05173667e39b834b645e35f41b71" "/opt/rustwide/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "27636d7642f2e9e2ebab7480526eae27b61d05173667e39b834b645e35f41b71", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=" "-e" "RUSTDOCFLAGS=" "-w" "/opt/rustwide/workdir" "--user" "0:0" "27636d7642f2e9e2ebab7480526eae27b61d05173667e39b834b645e35f41b71" "/opt/rustwide/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "fix" "--allow-no-vcs" "--allow-dirty" "--frozen" "--all" "--all-targets" "--message-format=json" "-Zfix-edition=end=2015,2024", kill_on_drop: false }`
[INFO] [stderr] crater-edition-check: migrating to next edition
[INFO] [stderr]    Migrating Cargo.toml from 2018 edition to 2021
[INFO] [stderr]    Compiling proc-macro2 v1.0.106
[INFO] [stderr]    Compiling proc-macro-hack v0.5.20+deprecated
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]    Compiling unindent v0.1.11
[INFO] [stderr]     Checking either v1.16.0
[INFO] [stderr]     Checking futures-core v0.3.32
[INFO] [stderr]     Checking send_wrapper v0.6.0
[INFO] [stderr]    Compiling lazy_static v1.5.0
[INFO] [stderr]    Compiling itertools v0.4.19
[INFO] [stderr]     Checking tokio v1.52.3
[INFO] [stderr]     Checking itertools v0.8.2
[INFO] [stderr]     Checking mockers v0.23.0 (/opt/rustwide/workdir)
[INFO] [stderr]    Migrating src/lib.rs from 2018 edition to 2021
[INFO] [stderr]    Compiling quote v1.0.46
[INFO] [stderr]    Compiling syn v2.0.118
[INFO] [stderr]    Compiling proc-quote-impl v0.3.2
[INFO] [stderr]     Checking tokio-stream v0.1.18
[INFO] [stderr]     Checking tokio-test v0.4.5
[INFO] [stderr]    Compiling proc-quote v0.4.0
[INFO] [stderr]    Compiling indoc-impl v0.3.6
[INFO] [stderr]    Compiling indoc v0.3.6
[INFO] [stderr]    Compiling mockers_derive v0.23.0
[INFO] [stderr]    Migrating tests/arbitrary_self.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/extern_trait.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/multi_trait.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/send.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/associated_types.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/named_mock_type.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/fluent.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/nested.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/cardinality.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/generic_trait.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/type_param_bounds.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/matchers.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/static_methods.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/lib.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/impl_trait.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/extern.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/struct.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/move.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/type_names.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/dyn_trait.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/clone.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/refs.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/fn_mut_reaction.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/async.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/derive.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/expect_in_action.rs from 2018 edition to 2021
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 16.64s
[INFO] [stderr] crater-edition-check: mockers v0.23.0 (/opt/rustwide/workdir) updating edition from 2018 to 2021
[INFO] [stderr]     Checking mockers v0.23.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: trait `MaybeDebug` is never used
[INFO] [stdout]  --> src/dbg.rs:5:7
[INFO] [stdout]   |
[INFO] [stdout] 5 | trait MaybeDebug {
[INFO] [stdout]   |       ^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: specialization is experimental
[INFO] [stdout]   --> src/dbg.rs:23:5
[INFO] [stdout]    |
[INFO] [stdout] 23 |     default fn fmt(&self, f: &mut Formatter<'_>) -> Result {
[INFO] [stdout]    |     ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: see issue #31844 <https://github.com/rust-lang/rust/issues/31844> for more information
[INFO] [stdout]    = help: add `#![feature(specialization)]` to the crate attributes to enable
[INFO] [stdout]    = note: this compiler was built on 2026-06-16; consider upgrading it if it is out of date
[INFO] [stdout]    = warning: unstable syntax can change at any point in the future, causing a hard error!
[INFO] [stdout]    = note: for more information, see issue #154045 <https://github.com/rust-lang/rust/issues/154045>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trait `A` is never used
[INFO] [stdout]  --> tests/nested.rs:6:15
[INFO] [stdout]   |
[INFO] [stdout] 6 |     pub trait A {
[INFO] [stdout]   |               ^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trait `MaybeDebug` is never used
[INFO] [stdout]  --> src/dbg.rs:5:7
[INFO] [stdout]   |
[INFO] [stdout] 5 | trait MaybeDebug {
[INFO] [stdout]   |       ^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: specialization is experimental
[INFO] [stdout]   --> src/dbg.rs:23:5
[INFO] [stdout]    |
[INFO] [stdout] 23 |     default fn fmt(&self, f: &mut Formatter<'_>) -> Result {
[INFO] [stdout]    |     ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: see issue #31844 <https://github.com/rust-lang/rust/issues/31844> for more information
[INFO] [stdout]    = help: add `#![feature(specialization)]` to the crate attributes to enable
[INFO] [stdout]    = note: this compiler was built on 2026-06-16; consider upgrading it if it is out of date
[INFO] [stdout]    = warning: unstable syntax can change at any point in the future, causing a hard error!
[INFO] [stdout]    = note: for more information, see issue #154045 <https://github.com/rust-lang/rust/issues/154045>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: impl trait in impl method signature does not match trait method signature
[INFO] [stdout]   --> tests/impl_trait.rs:23:30
[INFO] [stdout]    |
[INFO] [stdout] 23 |         #[mocked(return_type=u32)]
[INFO] [stdout]    |                              ^^^
[INFO] [stdout] 24 |         fn foo(&self) -> impl Sized;
[INFO] [stdout]    |                          ---------- return type from trait method defined here
[INFO] [stdout]    |
[INFO] [stdout]    = note: add `#[allow(refining_impl_trait)]` if it is intended for this to be part of the public API of this crate
[INFO] [stdout]    = note: we are soliciting feedback, see issue #121718 <https://github.com/rust-lang/rust/issues/121718> for more information
[INFO] [stdout]    = note: `#[warn(refining_impl_trait_internal)]` (part of `#[warn(refining_impl_trait)]`) on by default
[INFO] [stdout] help: replace the return type so that it matches the trait
[INFO] [stdout]    |
[INFO] [stdout] 23 -         #[mocked(return_type=u32)]
[INFO] [stdout] 23 +         #[mocked(return_type=impl Sized)]
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trait `A` is never used
[INFO] [stdout]    --> tests/multi_trait.rs:163:15
[INFO] [stdout]     |
[INFO] [stdout] 163 |     pub trait A {
[INFO] [stdout]     |               ^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trait `B` is never used
[INFO] [stdout]    --> tests/multi_trait.rs:167:15
[INFO] [stdout]     |
[INFO] [stdout] 167 |     pub trait B: A {
[INFO] [stdout]     |               ^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 18.36s
[INFO] [stderr] crater-edition-check: migrating to next edition
[INFO] [stderr]    Migrating Cargo.toml from 2018 edition to 2021
[INFO] [stderr]     Checking mockers v0.23.0 (/opt/rustwide/workdir)
[INFO] [stderr]    Migrating src/lib.rs from 2021 edition to 2024
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]  --> src/colors.rs:4:15
[INFO] [stdout]   |
[INFO] [stdout] 4 |     (bold: $s:expr) => {
[INFO] [stdout]   |               ^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = warning: this changes meaning in Rust 2024
[INFO] [stdout]   = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout]   = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility`
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]   |
[INFO] [stdout] 4 |     (bold: $s:expr_2021) => {
[INFO] [stdout]   |                   +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: errors present after applying fixes to crate `mockers`
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]  --> src/colors.rs:7:14
[INFO] [stdout]   |
[INFO] [stdout] 7 |     (red: $s:expr) => {
[INFO] [stdout]   |              ^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = warning: this changes meaning in Rust 2024
[INFO] [stdout]   = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]   |
[INFO] [stdout] 7 |     (red: $s:expr_2021) => {
[INFO] [stdout]   |                  +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]  --> src/lib.rs
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:10:19
[INFO] [stdout]    |
[INFO] [stdout] 10 |     (red_bold: $s:expr) => {
[INFO] [stdout]    |                   ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 10 |     (red_bold: $s:expr_2021) => {
[INFO] [stdout]    |                       +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]   = cause: error[E0800]: cannot find type or const parameter `Arg0` in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:13:16
[INFO] [stdout]    |
[INFO] [stdout] 13 |     (green: $s:expr) => {
[INFO] [stdout]    |                ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 13 |     (green: $s:expr_2021) => {
[INFO] [stdout]    |                    +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                --> src/lib.rs:1097:41
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:16:21
[INFO] [stdout]    |
[INFO] [stdout] 16 |     (green_bold: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 16 |     (green_bold: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:19:17
[INFO] [stdout]    |
[INFO] [stdout] 19 |     (orange: $s:expr) => {
[INFO] [stdout]    |                 ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 19 |     (orange: $s:expr_2021) => {
[INFO] [stdout]    |                     +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:22:22
[INFO] [stdout]    |
[INFO] [stdout] 22 |     (yellow_bold: $s:expr) => {
[INFO] [stdout]    |                      ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 22 |     (yellow_bold: $s:expr_2021) => {
[INFO] [stdout]    |                          +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |                                         ^^^^ not found in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:25:15
[INFO] [stdout]    |
[INFO] [stdout] 25 |     (blue: $s:expr) => {
[INFO] [stdout]    |               ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 25 |     (blue: $s:expr_2021) => {
[INFO] [stdout]    |                   +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            ...
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:28:20
[INFO] [stdout]    |
[INFO] [stdout] 28 |     (blue_bold: $s:expr) => {
[INFO] [stdout]    |                    ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 28 |     (blue_bold: $s:expr_2021) => {
[INFO] [stdout]    |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1125 |     define_verify!(verify0 { });
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:31:17
[INFO] [stdout]    |
[INFO] [stdout] 31 |     (purple: $s:expr) => {
[INFO] [stdout]    |                 ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 31 |     (purple: $s:expr_2021) => {
[INFO] [stdout]    |                     +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |     --------------------------- in this macro invocation
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:34:22
[INFO] [stdout]    |
[INFO] [stdout] 34 |     (purple_bold: $s:expr) => {
[INFO] [stdout]    |                      ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 34 |     (purple_bold: $s:expr_2021) => {
[INFO] [stdout]    |                          +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:37:15
[INFO] [stdout]    |
[INFO] [stdout] 37 |     (cyan: $s:expr) => {
[INFO] [stdout]    |               ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 37 |     (cyan: $s:expr_2021) => {
[INFO] [stdout]    |                   +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:40:20
[INFO] [stdout]    |
[INFO] [stdout] 40 |     (cyan_bold: $s:expr) => {
[INFO] [stdout]    |                    ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 40 |     (cyan_bold: $s:expr_2021) => {
[INFO] [stdout]    |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:43:21
[INFO] [stdout]    |
[INFO] [stdout] 43 |     (light_grey: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 43 |     (light_grey: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:46:21
[INFO] [stdout]    |
[INFO] [stdout] 46 |     (white_bold: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 46 |     (white_bold: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg1` in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:49:20
[INFO] [stdout]    |
[INFO] [stdout] 49 |     (dark_grey: $s:expr) => {
[INFO] [stdout]    |                    ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 49 |     (dark_grey: $s:expr_2021) => {
[INFO] [stdout]    |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                --> src/lib.rs:1097:47
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:52:25
[INFO] [stdout]    |
[INFO] [stdout] 52 |     (dark_grey_bold: $s:expr) => {
[INFO] [stdout]    |                         ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 52 |     (dark_grey_bold: $s:expr_2021) => {
[INFO] [stdout]    |                             +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:55:16
[INFO] [stdout]    |
[INFO] [stdout] 55 |     (peach: $s:expr) => {
[INFO] [stdout]    |                ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 55 |     (peach: $s:expr_2021) => {
[INFO] [stdout]    |                    +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:58:21
[INFO] [stdout]    |
[INFO] [stdout] 58 |     (peach_bold: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 58 |     (peach_bold: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |                                               ^^^^ not found in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:61:15
[INFO] [stdout]    |
[INFO] [stdout] 61 |     (lime: $s:expr) => {
[INFO] [stdout]    |               ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 61 |     (lime: $s:expr_2021) => {
[INFO] [stdout]    |                   +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            ...
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:64:20
[INFO] [stdout]    |
[INFO] [stdout] 64 |     (lime_bold: $s:expr) => {
[INFO] [stdout]    |                    ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 64 |     (lime_bold: $s:expr_2021) => {
[INFO] [stdout]    |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1125 |     define_verify!(verify0 { });
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:67:17
[INFO] [stdout]    |
[INFO] [stdout] 67 |     (yellow: $s:expr) => {
[INFO] [stdout]    |                 ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 67 |     (yellow: $s:expr_2021) => {
[INFO] [stdout]    |                     +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |     --------------------------- in this macro invocation
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:70:22
[INFO] [stdout]    |
[INFO] [stdout] 70 |     (yellow_bold: $s:expr) => {
[INFO] [stdout]    |                      ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 70 |     (yellow_bold: $s:expr_2021) => {
[INFO] [stdout]    |                          +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:73:21
[INFO] [stdout]    |
[INFO] [stdout] 73 |     (royal_blue: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 73 |     (royal_blue: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:76:26
[INFO] [stdout]    |
[INFO] [stdout] 76 |     (royal_blue_bold: $s:expr) => {
[INFO] [stdout]    |                          ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 76 |     (royal_blue_bold: $s:expr_2021) => {
[INFO] [stdout]    |                              +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:79:18
[INFO] [stdout]    |
[INFO] [stdout] 79 |     (magenta: $s:expr) => {
[INFO] [stdout]    |                  ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 79 |     (magenta: $s:expr_2021) => {
[INFO] [stdout]    |                      +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:82:23
[INFO] [stdout]    |
[INFO] [stdout] 82 |     (magenta_bold: $s:expr) => {
[INFO] [stdout]    |                       ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 82 |     (magenta_bold: $s:expr_2021) => {
[INFO] [stdout]    |                           +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg2` in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:85:15
[INFO] [stdout]    |
[INFO] [stdout] 85 |     (teal: $s:expr) => {
[INFO] [stdout]    |               ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 85 |     (teal: $s:expr_2021) => {
[INFO] [stdout]    |                   +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                --> src/lib.rs:1097:53
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:88:20
[INFO] [stdout]    |
[INFO] [stdout] 88 |     (teal_bold: $s:expr) => {
[INFO] [stdout]    |                    ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 88 |     (teal_bold: $s:expr_2021) => {
[INFO] [stdout]    |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:91:16
[INFO] [stdout]    |
[INFO] [stdout] 91 |     (white: $s:expr) => {
[INFO] [stdout]    |                ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 91 |     (white: $s:expr_2021) => {
[INFO] [stdout]    |                    +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:94:21
[INFO] [stdout]    |
[INFO] [stdout] 94 |     (white_bold: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 94 |     (white_bold: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |                                                     ^^^^ not found in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]    --> src/matchers/mod.rs:119:58
[INFO] [stdout]     |
[INFO] [stdout] 119 |     ($func_name:ident, $class_name:ident, $comp:tt, $msg:expr, $($bounds:tt)+) => {
[INFO] [stdout]     |                                                          ^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]     |
[INFO] [stdout] 119 |     ($func_name:ident, $class_name:ident, $comp:tt, $msg:expr_2021, $($bounds:tt)+) => {
[INFO] [stdout]     |                                                              +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            ...
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]    --> src/matchers/mod.rs:333:9
[INFO] [stdout]     |
[INFO] [stdout] 333 |     ($e:expr) => {{
[INFO] [stdout]     |         ^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]     |
[INFO] [stdout] 333 |     ($e:expr_2021) => {{
[INFO] [stdout]     |             +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1125 |     define_verify!(verify0 { });
[INFO] [stdout] warning: `impl FnOnce() -> Res` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds
[INFO] [stdout]     --> src/lib.rs:1096:13
[INFO] [stdout]      |
[INFO] [stdout] 1096 |             &mut self, method_data: MethodData$(, $arg: $Arg)*
[INFO] [stdout]      |             ^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout]      = warning: this changes meaning in Rust 2024
[INFO] [stdout]      = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]      = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility`
[INFO] [stdout]      = note: this warning originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res + use<Res> {
[INFO] [stdout]      |                                   ++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |     --------------------------- in this macro invocation
[INFO] [stdout] warning: `impl FnOnce() -> Res` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds
[INFO] [stdout]     --> src/lib.rs:1096:13
[INFO] [stdout]      |
[INFO] [stdout] 1096 |             &mut self, method_data: MethodData$(, $arg: $Arg)*
[INFO] [stdout]      |             ^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout]      = warning: this changes meaning in Rust 2024
[INFO] [stdout]      = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]      = note: this warning originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Res> {
[INFO] [stdout]      |                                   ++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: `impl FnOnce() -> Res` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1127 |     define_verify!(verify2 { (0, arg0, Arg0), (1, arg1, Arg1) });
[INFO] [stdout]      |     ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds
[INFO] [stdout]     --> src/lib.rs:1096:13
[INFO] [stdout]      |
[INFO] [stdout] 1096 |             &mut self, method_data: MethodData$(, $arg: $Arg)*
[INFO] [stdout]      |             ^
[INFO] [stdout] ...
[INFO] [stdout] 1127 |     define_verify!(verify2 { (0, arg0, Arg0), (1, arg1, Arg1) });
[INFO] [stdout]      |     ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout]      = warning: this changes meaning in Rust 2024
[INFO] [stdout]      = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]      = note: this warning originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Res> {
[INFO] [stdout]      |                                   ++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] warning: `impl FnOnce() -> Res` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1128 |     define_verify!(verify3 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2) });
[INFO] [stdout]      |     ----------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds
[INFO] [stdout]     --> src/lib.rs:1096:13
[INFO] [stdout]      |
[INFO] [stdout] 1096 |             &mut self, method_data: MethodData$(, $arg: $Arg)*
[INFO] [stdout]      |             ^
[INFO] [stdout] ...
[INFO] [stdout] 1128 |     define_verify!(verify3 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2) });
[INFO] [stdout]      |     ----------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout]      = warning: this changes meaning in Rust 2024
[INFO] [stdout]      = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]      = note: this warning originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Res> {
[INFO] [stdout]      |                                   ++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            
[INFO] [stdout] warning: `impl FnOnce() -> Res` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1129 |     define_verify!(verify4 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2), (3, arg3, Arg3) });
[INFO] [stdout]      |     ---------------------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds
[INFO] [stdout]     --> src/lib.rs:1096:13
[INFO] [stdout]      |
[INFO] [stdout] 1096 |             &mut self, method_data: MethodData$(, $arg: $Arg)*
[INFO] [stdout]      |             ^
[INFO] [stdout] ...
[INFO] [stdout] 1129 |     define_verify!(verify4 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2), (3, arg3, Arg3) });
[INFO] [stdout]      |     ---------------------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout]      = warning: this changes meaning in Rust 2024
[INFO] [stdout]      = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]      = note: this warning originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stdout]      |                                   ++++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg3` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:59
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                           ^^^^ not found in this scope
[INFO] [stderr]            ...
[INFO] [stderr]            1125 |     define_verify!(verify0 { });
[INFO] [stderr]                 |     --------------------------- in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg1` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:47
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                               ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stderr]                 |     -------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg0, Arg2, Arg3, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg2` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:53
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                     ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stderr]                 |     -------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg0, Arg3, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg3` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:59
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                           ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stderr]                 |     -------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg0, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg2` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:53
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                     ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1127 |     define_verify!(verify2 { (0, arg0, Arg0), (1, arg1, Arg1) });
[INFO] [stderr]                 |     ------------------------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg0, Arg3, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg3` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:59
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                           ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1127 |     define_verify!(verify2 { (0, arg0, Arg0), (1, arg1, Arg1) });
[INFO] [stderr]                 |     ------------------------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg0, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg3` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:59
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                           ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1128 |     define_verify!(verify3 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2) });
[INFO] [stderr]                 |     -----------------------------------------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg0, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error: aborting due to 10 previous errors
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            For more information about this error, try `rustc --explain E0800`.
[INFO] [stderr] help: to report this as a bug, open an issue at https://github.com/rust-lang/rust/issues, quoting the full output of this command
[INFO] [stderr] help: to possibly apply more fixes, pass in the `--broken-code` flag
[INFO] [stderr] note: original diagnostics will follow:
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]  --> src/colors.rs:4:15
[INFO] [stdout]   |
[INFO] [stdout] 4 |     (bold: $s:expr) => {
[INFO] [stdout]   |               ^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = warning: this changes meaning in Rust 2024
[INFO] [stdout]   = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout]   = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility`
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]   |
[INFO] [stdout] 4 |     (bold: $s:expr_2021) => {
[INFO] [stdout]   |                   +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]  --> src/colors.rs:7:14
[INFO] [stdout]   |
[INFO] [stdout] 7 |     (red: $s:expr) => {
[INFO] [stdout]   |              ^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = warning: this changes meaning in Rust 2024
[INFO] [stdout]   = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]   |
[INFO] [stdout] 7 |     (red: $s:expr_2021) => {
[INFO] [stdout]   |                  +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:10:19
[INFO] [stdout]    |
[INFO] [stdout] 10 |     (red_bold: $s:expr) => {
[INFO] [stdout]    |                   ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 10 |     (red_bold: $s:expr_2021) => {
[INFO] [stdout]    |                       +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:13:16
[INFO] [stdout]    |
[INFO] [stdout] 13 |     (green: $s:expr) => {
[INFO] [stdout]    |                ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 13 |     (green: $s:expr_2021) => {
[INFO] [stdout]    |                    +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: errors present after applying fixes to crate `mockers`
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:16:21
[INFO] [stdout]    |
[INFO] [stdout] 16 |     (green_bold: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 16 |     (green_bold: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]  --> src/lib.rs
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:19:17
[INFO] [stdout]    |
[INFO] [stdout] 19 |     (orange: $s:expr) => {
[INFO] [stdout]    |                 ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 19 |     (orange: $s:expr_2021) => {
[INFO] [stdout]    |                     +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]   = cause: error[E0800]: cannot find type or const parameter `Arg0` in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:22:22
[INFO] [stdout]    |
[INFO] [stdout] 22 |     (yellow_bold: $s:expr) => {
[INFO] [stdout]    |                      ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 22 |     (yellow_bold: $s:expr_2021) => {
[INFO] [stdout]    |                          +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                --> src/lib.rs:1097:41
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:25:15
[INFO] [stdout]    |
[INFO] [stdout] 25 |     (blue: $s:expr) => {
[INFO] [stdout]    |               ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 25 |     (blue: $s:expr_2021) => {
[INFO] [stdout]    |                   +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:28:20
[INFO] [stdout]    |
[INFO] [stdout] 28 |     (blue_bold: $s:expr) => {
[INFO] [stdout]    |                    ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 28 |     (blue_bold: $s:expr_2021) => {
[INFO] [stdout]    |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:31:17
[INFO] [stdout]    |
[INFO] [stdout] 31 |     (purple: $s:expr) => {
[INFO] [stdout]    |                 ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 31 |     (purple: $s:expr_2021) => {
[INFO] [stdout]    |                     +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |                                         ^^^^ not found in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:34:22
[INFO] [stdout]    |
[INFO] [stdout] 34 |     (purple_bold: $s:expr) => {
[INFO] [stdout]    |                      ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 34 |     (purple_bold: $s:expr_2021) => {
[INFO] [stdout]    |                          +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            ...
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:37:15
[INFO] [stdout]    |
[INFO] [stdout] 37 |     (cyan: $s:expr) => {
[INFO] [stdout]    |               ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 37 |     (cyan: $s:expr_2021) => {
[INFO] [stdout]    |                   +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1125 |     define_verify!(verify0 { });
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:40:20
[INFO] [stdout]    |
[INFO] [stdout] 40 |     (cyan_bold: $s:expr) => {
[INFO] [stdout]    |                    ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 40 |     (cyan_bold: $s:expr_2021) => {
[INFO] [stdout]    |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |     --------------------------- in this macro invocation
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:43:21
[INFO] [stdout]    |
[INFO] [stdout] 43 |     (light_grey: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 43 |     (light_grey: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:46:21
[INFO] [stdout]    |
[INFO] [stdout] 46 |     (white_bold: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 46 |     (white_bold: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:49:20
[INFO] [stdout]    |
[INFO] [stdout] 49 |     (dark_grey: $s:expr) => {
[INFO] [stdout]    |                    ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 49 |     (dark_grey: $s:expr_2021) => {
[INFO] [stdout]    |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:52:25
[INFO] [stdout]    |
[INFO] [stdout] 52 |     (dark_grey_bold: $s:expr) => {
[INFO] [stdout]    |                         ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 52 |     (dark_grey_bold: $s:expr_2021) => {
[INFO] [stdout]    |                             +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:55:16
[INFO] [stdout]    |
[INFO] [stdout] 55 |     (peach: $s:expr) => {
[INFO] [stdout]    |                ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 55 |     (peach: $s:expr_2021) => {
[INFO] [stdout]    |                    +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg1` in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:58:21
[INFO] [stdout]    |
[INFO] [stdout] 58 |     (peach_bold: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 58 |     (peach_bold: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                --> src/lib.rs:1097:47
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:61:15
[INFO] [stdout]    |
[INFO] [stdout] 61 |     (lime: $s:expr) => {
[INFO] [stdout]    |               ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 61 |     (lime: $s:expr_2021) => {
[INFO] [stdout]    |                   +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:64:20
[INFO] [stdout]    |
[INFO] [stdout] 64 |     (lime_bold: $s:expr) => {
[INFO] [stdout]    |                    ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 64 |     (lime_bold: $s:expr_2021) => {
[INFO] [stdout]    |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:67:17
[INFO] [stdout]    |
[INFO] [stdout] 67 |     (yellow: $s:expr) => {
[INFO] [stdout]    |                 ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 67 |     (yellow: $s:expr_2021) => {
[INFO] [stdout]    |                     +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |                                               ^^^^ not found in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:70:22
[INFO] [stdout]    |
[INFO] [stdout] 70 |     (yellow_bold: $s:expr) => {
[INFO] [stdout]    |                      ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 70 |     (yellow_bold: $s:expr_2021) => {
[INFO] [stdout]    |                          +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            ...
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:73:21
[INFO] [stdout]    |
[INFO] [stdout] 73 |     (royal_blue: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 73 |     (royal_blue: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1125 |     define_verify!(verify0 { });
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:76:26
[INFO] [stdout]    |
[INFO] [stdout] 76 |     (royal_blue_bold: $s:expr) => {
[INFO] [stdout]    |                          ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 76 |     (royal_blue_bold: $s:expr_2021) => {
[INFO] [stdout]    |                              +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |     --------------------------- in this macro invocation
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:79:18
[INFO] [stdout]    |
[INFO] [stdout] 79 |     (magenta: $s:expr) => {
[INFO] [stdout]    |                  ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 79 |     (magenta: $s:expr_2021) => {
[INFO] [stdout]    |                      +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:82:23
[INFO] [stdout]    |
[INFO] [stdout] 82 |     (magenta_bold: $s:expr) => {
[INFO] [stdout]    |                       ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 82 |     (magenta_bold: $s:expr_2021) => {
[INFO] [stdout]    |                           +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:85:15
[INFO] [stdout]    |
[INFO] [stdout] 85 |     (teal: $s:expr) => {
[INFO] [stdout]    |               ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 85 |     (teal: $s:expr_2021) => {
[INFO] [stdout]    |                   +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:88:20
[INFO] [stdout]    |
[INFO] [stdout] 88 |     (teal_bold: $s:expr) => {
[INFO] [stdout]    |                    ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 88 |     (teal_bold: $s:expr_2021) => {
[INFO] [stdout]    |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:91:16
[INFO] [stdout]    |
[INFO] [stdout] 91 |     (white: $s:expr) => {
[INFO] [stdout]    |                ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 91 |     (white: $s:expr_2021) => {
[INFO] [stdout]    |                    +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg2` in this scope
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/colors.rs:94:21
[INFO] [stdout]    |
[INFO] [stdout] 94 |     (white_bold: $s:expr) => {
[INFO] [stdout]    |                     ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 94 |     (white_bold: $s:expr_2021) => {
[INFO] [stdout]    |                         +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                --> src/lib.rs:1097:53
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]    --> src/matchers/mod.rs:119:58
[INFO] [stdout]     |
[INFO] [stdout] 119 |     ($func_name:ident, $class_name:ident, $comp:tt, $msg:expr, $($bounds:tt)+) => {
[INFO] [stdout]     |                                                          ^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]     |
[INFO] [stdout] 119 |     ($func_name:ident, $class_name:ident, $comp:tt, $msg:expr_2021, $($bounds:tt)+) => {
[INFO] [stdout]     |                                                              +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]    --> src/matchers/mod.rs:333:9
[INFO] [stdout]     |
[INFO] [stdout] 333 |     ($e:expr) => {{
[INFO] [stdout]     |         ^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]     |
[INFO] [stdout] 333 |     ($e:expr_2021) => {{
[INFO] [stdout]     |             +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stdout] warning: `impl FnOnce() -> Res` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds
[INFO] [stdout]     --> src/lib.rs:1096:13
[INFO] [stdout]      |
[INFO] [stdout] 1096 |             &mut self, method_data: MethodData$(, $arg: $Arg)*
[INFO] [stdout]      |             ^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout]      = warning: this changes meaning in Rust 2024
[INFO] [stdout]      = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]      = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility`
[INFO] [stdout]      = note: this warning originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res + use<Res> {
[INFO] [stdout]      |                                   ++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |                                                     ^^^^ not found in this scope
[INFO] [stdout] warning: `impl FnOnce() -> Res` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds
[INFO] [stdout]     --> src/lib.rs:1096:13
[INFO] [stdout]      |
[INFO] [stdout] 1096 |             &mut self, method_data: MethodData$(, $arg: $Arg)*
[INFO] [stdout]      |             ^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout]      = warning: this changes meaning in Rust 2024
[INFO] [stdout]      = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]      = note: this warning originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Res> {
[INFO] [stdout]      |                                   ++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            ...
[INFO] [stdout] warning: `impl FnOnce() -> Res` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1127 |     define_verify!(verify2 { (0, arg0, Arg0), (1, arg1, Arg1) });
[INFO] [stdout]      |     ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds
[INFO] [stdout]     --> src/lib.rs:1096:13
[INFO] [stdout]      |
[INFO] [stdout] 1096 |             &mut self, method_data: MethodData$(, $arg: $Arg)*
[INFO] [stdout]      |             ^
[INFO] [stdout] ...
[INFO] [stdout] 1127 |     define_verify!(verify2 { (0, arg0, Arg0), (1, arg1, Arg1) });
[INFO] [stdout]      |     ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout]      = warning: this changes meaning in Rust 2024
[INFO] [stdout]      = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]      = note: this warning originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Res> {
[INFO] [stdout]      |                                   ++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]            1125 |     define_verify!(verify0 { });
[INFO] [stdout] warning: `impl FnOnce() -> Res` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1128 |     define_verify!(verify3 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2) });
[INFO] [stdout]      |     ----------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds
[INFO] [stdout]     --> src/lib.rs:1096:13
[INFO] [stdout]      |
[INFO] [stdout] 1096 |             &mut self, method_data: MethodData$(, $arg: $Arg)*
[INFO] [stdout]      |             ^
[INFO] [stdout] ...
[INFO] [stdout] 1128 |     define_verify!(verify3 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2) });
[INFO] [stdout]      |     ----------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout]      = warning: this changes meaning in Rust 2024
[INFO] [stdout]      = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]      = note: this warning originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Res> {
[INFO] [stdout]      |                                   ++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |     --------------------------- in this macro invocation
[INFO] [stdout] warning: `impl FnOnce() -> Res` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1129 |     define_verify!(verify4 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2), (3, arg3, Arg3) });
[INFO] [stdout]      |     ---------------------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds
[INFO] [stdout]     --> src/lib.rs:1096:13
[INFO] [stdout]      |
[INFO] [stdout] 1096 |             &mut self, method_data: MethodData$(, $arg: $Arg)*
[INFO] [stdout]      |             ^
[INFO] [stdout] ...
[INFO] [stdout] 1129 |     define_verify!(verify4 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2), (3, arg3, Arg3) });
[INFO] [stdout]      |     ---------------------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout]      = warning: this changes meaning in Rust 2024
[INFO] [stdout]      = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]      = note: this warning originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stdout]      |                                   ++++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg3` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:59
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                           ^^^^ not found in this scope
[INFO] [stderr]            ...
[INFO] [stderr]            1125 |     define_verify!(verify0 { });
[INFO] [stderr]                 |     --------------------------- in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg1` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:47
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                               ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stderr]                 |     -------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg0, Arg2, Arg3, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg2` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:53
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                     ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stderr]                 |     -------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg0, Arg3, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg3` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:59
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                           ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stderr]                 |     -------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg0, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg2` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:53
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                     ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1127 |     define_verify!(verify2 { (0, arg0, Arg0), (1, arg1, Arg1) });
[INFO] [stderr]                 |     ------------------------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg0, Arg3, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg3` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:59
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                           ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1127 |     define_verify!(verify2 { (0, arg0, Arg0), (1, arg1, Arg1) });
[INFO] [stderr]                 |     ------------------------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg0, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error[E0800]: cannot find type or const parameter `Arg3` in this scope
[INFO] [stderr]                --> src/lib.rs:1097:59
[INFO] [stderr]                 |
[INFO] [stderr]            1097 |         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]                 |                                                           ^^^^
[INFO] [stderr]            ...
[INFO] [stderr]            1128 |     define_verify!(verify3 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2) });
[INFO] [stderr]                 |     -----------------------------------------------------------------------------
[INFO] [stderr]                 |     |                                  |
[INFO] [stderr]                 |     |                                  similarly named type parameter `Arg0` defined here
[INFO] [stderr]                 |     in this macro invocation
[INFO] [stderr]                 |
[INFO] [stderr]                 = note: this error originates in the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]            help: a type parameter with a similar name exists
[INFO] [stderr]                 |
[INFO] [stderr]            1097 -         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg3, Res> {
[INFO] [stderr]            1097 +         ) -> impl FnOnce() -> Res + use<Arg0, Arg1, Arg2, Arg0, Res> {
[INFO] [stderr]                 |
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            error: aborting due to 10 previous errors
[INFO] [stderr]            
[INFO] [stderr]            
[INFO] [stderr]            For more information about this error, try `rustc --explain E0800`.
[INFO] [stderr] help: to report this as a bug, open an issue at https://github.com/rust-lang/rust/issues, quoting the full output of this command
[INFO] [stderr] help: to possibly apply more fixes, pass in the `--broken-code` flag
[INFO] [stderr] note: original diagnostics will follow:
[INFO] [stderr]    Migrating tests/lib.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/expect_in_action.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/derive.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/fn_mut_reaction.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/send.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/async.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/matchers.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/struct.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/associated_types.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/extern_trait.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/static_methods.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/refs.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/move.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/cardinality.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/generic_trait.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/nested.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/impl_trait.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/clone.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/dyn_trait.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/named_mock_type.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/type_names.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/arbitrary_self.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/extern.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/fluent.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/multi_trait.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/type_param_bounds.rs from 2021 edition to 2024
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 24.46s
[INFO] [stderr] crater-edition-check: mockers v0.23.0 (/opt/rustwide/workdir) updating edition from 2021 to 2024
[INFO] [stderr]     Checking mockers v0.23.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: trait `MaybeDebug` is never used
[INFO] [stdout]  --> src/dbg.rs:5:7
[INFO] [stdout]   |
[INFO] [stdout] 5 | trait MaybeDebug {
[INFO] [stdout]   |       ^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: specialization is experimental
[INFO] [stdout]   --> src/dbg.rs:23:5
[INFO] [stdout]    |
[INFO] [stdout] 23 |     default fn fmt(&self, f: &mut Formatter<'_>) -> Result {
[INFO] [stdout]    |     ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: see issue #31844 <https://github.com/rust-lang/rust/issues/31844> for more information
[INFO] [stdout]    = help: add `#![feature(specialization)]` to the crate attributes to enable
[INFO] [stdout]    = note: this compiler was built on 2026-06-16; consider upgrading it if it is out of date
[INFO] [stdout]    = warning: unstable syntax can change at any point in the future, causing a hard error!
[INFO] [stdout]    = note: for more information, see issue #154045 <https://github.com/rust-lang/rust/issues/154045>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trait `MaybeDebug` is never used
[INFO] [stdout]  --> src/dbg.rs:5:7
[INFO] [stdout]   |
[INFO] [stdout] 5 | trait MaybeDebug {
[INFO] [stdout]   |       ^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: specialization is experimental
[INFO] [stdout]   --> src/dbg.rs:23:5
[INFO] [stdout]    |
[INFO] [stdout] 23 |     default fn fmt(&self, f: &mut Formatter<'_>) -> Result {
[INFO] [stdout]    |     ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: see issue #31844 <https://github.com/rust-lang/rust/issues/31844> for more information
[INFO] [stdout]    = help: add `#![feature(specialization)]` to the crate attributes to enable
[INFO] [stdout]    = note: this compiler was built on 2026-06-16; consider upgrading it if it is out of date
[INFO] [stdout]    = warning: unstable syntax can change at any point in the future, causing a hard error!
[INFO] [stdout]    = note: for more information, see issue #154045 <https://github.com/rust-lang/rust/issues/154045>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/derive.rs:5:1
[INFO] [stdout]      |
[INFO] [stdout]    5 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/derive.rs:5:1
[INFO] [stdout]      |
[INFO] [stdout]    5 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Arg1, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1127 |     define_verify!(verify2 { (0, arg0, Arg0), (1, arg1, Arg1) });
[INFO] [stdout]      |     ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "derive") due to 1 previous error
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/type_param_bounds.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked(debug)]
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/type_param_bounds.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked(debug)]
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "type_param_bounds") due to 1 previous error
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/associated_types.rs:5:1
[INFO] [stdout]      |
[INFO] [stdout]    5 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/associated_types.rs:5:1
[INFO] [stdout]      |
[INFO] [stdout]    5 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/nested.rs:11:1
[INFO] [stdout]      |
[INFO] [stdout]   11 | / mock! {
[INFO] [stdout]   12 | |     AMock,
[INFO] [stdout]   13 | |     nested,
[INFO] [stdout]   14 | |     trait A {
[INFO] [stdout] ...    |
[INFO] [stdout]   17 | | }
[INFO] [stdout]      | | ^
[INFO] [stdout]      | | |
[INFO] [stdout]      | |_move out of value occurs here
[INFO] [stdout]      |   borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/nested.rs:11:1
[INFO] [stdout]      |
[INFO] [stdout]   11 | / mock! {
[INFO] [stdout]   12 | |     AMock,
[INFO] [stdout]   13 | |     nested,
[INFO] [stdout]   14 | |     trait A {
[INFO] [stdout] ...    |
[INFO] [stdout]   17 | | }
[INFO] [stdout]      | |_^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the macro `mock` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/associated_types.rs:11:1
[INFO] [stdout]      |
[INFO] [stdout]   11 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/associated_types.rs:11:1
[INFO] [stdout]      |
[INFO] [stdout]   11 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/clone.rs:14:1
[INFO] [stdout]      |
[INFO] [stdout]   14 | / mock! {
[INFO] [stdout]   15 | |     AShared,
[INFO] [stdout]   16 | |     self,
[INFO] [stdout]   17 | |     trait A {
[INFO] [stdout] ...    |
[INFO] [stdout]   20 | | }
[INFO] [stdout]      | | ^
[INFO] [stdout]      | | |
[INFO] [stdout]      | |_move out of value occurs here
[INFO] [stdout]      |   borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/clone.rs:14:1
[INFO] [stdout]      |
[INFO] [stdout]   14 | / mock! {
[INFO] [stdout]   15 | |     AShared,
[INFO] [stdout]   16 | |     self,
[INFO] [stdout]   17 | |     trait A {
[INFO] [stdout] ...    |
[INFO] [stdout]   20 | | }
[INFO] [stdout]      | |_^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the macro `mock` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/multi_trait.rs:12:5
[INFO] [stdout]      |
[INFO] [stdout]   12 |     #[mocked(module = "crate::derive_inherited_trait")]
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |     |
[INFO] [stdout]      |     move out of value occurs here
[INFO] [stdout]      |     borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/multi_trait.rs:12:5
[INFO] [stdout]      |
[INFO] [stdout]   12 |     #[mocked(module = "crate::derive_inherited_trait")]
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/multi_trait.rs:17:5
[INFO] [stdout]      |
[INFO] [stdout]   17 |     #[mocked(refs = "A => crate::derive_inherited_trait::A")]
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |     |
[INFO] [stdout]      |     move out of value occurs here
[INFO] [stdout]      |     borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/multi_trait.rs:17:5
[INFO] [stdout]      |
[INFO] [stdout]   17 |     #[mocked(refs = "A => crate::derive_inherited_trait::A")]
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/clone.rs:24:1
[INFO] [stdout]      |
[INFO] [stdout]   24 | / mock! {
[INFO] [stdout]   25 | |     AMock,
[INFO] [stdout]   26 | |     self,
[INFO] [stdout]   27 | |     trait A {
[INFO] [stdout] ...    |
[INFO] [stdout]   30 | | }
[INFO] [stdout]      | | ^
[INFO] [stdout]      | | |
[INFO] [stdout]      | |_move out of value occurs here
[INFO] [stdout]      |   borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/clone.rs:24:1
[INFO] [stdout]      |
[INFO] [stdout]   24 | / mock! {
[INFO] [stdout]   25 | |     AMock,
[INFO] [stdout]   26 | |     self,
[INFO] [stdout]   27 | |     trait A {
[INFO] [stdout] ...    |
[INFO] [stdout]   30 | | }
[INFO] [stdout]      | |_^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the macro `mock` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/clone.rs:31:1
[INFO] [stdout]      |
[INFO] [stdout]   31 | mock_clone!(AMock, AMockHandle);
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      | borrow later used here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/clone.rs:31:1
[INFO] [stdout]      |
[INFO] [stdout]   31 | mock_clone!(AMock, AMockHandle);
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the macro `mock_clone` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/clone.rs:33:1
[INFO] [stdout]      |
[INFO] [stdout]   33 | #[mocked(derive(Clone))]
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/clone.rs:33:1
[INFO] [stdout]      |
[INFO] [stdout]   33 | #[mocked(derive(Clone))]
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/multi_trait.rs:42:9
[INFO] [stdout]      |
[INFO] [stdout]   42 |         #[mocked(module = "crate::derive_inherited_trait_different_modules::a")]
[INFO] [stdout]      |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |         |
[INFO] [stdout]      |         move out of value occurs here
[INFO] [stdout]      |         borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/multi_trait.rs:42:9
[INFO] [stdout]      |
[INFO] [stdout]   42 |         #[mocked(module = "crate::derive_inherited_trait_different_modules::a")]
[INFO] [stdout]      |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/multi_trait.rs:51:9
[INFO] [stdout]      |
[INFO] [stdout]   51 |         #[mocked(refs = "super::a::A => crate::derive_inherited_trait_different_modules::a::A")]
[INFO] [stdout]      |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |         |
[INFO] [stdout]      |         move out of value occurs here
[INFO] [stdout]      |         borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/multi_trait.rs:51:9
[INFO] [stdout]      |
[INFO] [stdout]   51 |         #[mocked(refs = "super::a::A => crate::derive_inherited_trait_different_modules::a::A")]
[INFO] [stdout]      |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/clone.rs:33:1
[INFO] [stdout]      |
[INFO] [stdout]   33 | #[mocked(derive(Clone))]
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/clone.rs:33:1
[INFO] [stdout]      |
[INFO] [stdout]   33 | #[mocked(derive(Clone))]
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/clone.rs:38:1
[INFO] [stdout]      |
[INFO] [stdout]   38 | #[mocked(derive(Clone(share_expectations)))]
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/clone.rs:38:1
[INFO] [stdout]      |
[INFO] [stdout]   38 | #[mocked(derive(Clone(share_expectations)))]
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/multi_trait.rs:86:5
[INFO] [stdout]      |
[INFO] [stdout]   86 | /     mock! {
[INFO] [stdout]   87 | |         BMock,
[INFO] [stdout]   88 | |
[INFO] [stdout]   89 | |         self,
[INFO] [stdout] ...    |
[INFO] [stdout]   98 | |     }
[INFO] [stdout]      | |     ^
[INFO] [stdout]      | |     |
[INFO] [stdout]      | |_____move out of value occurs here
[INFO] [stdout]      |       borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/multi_trait.rs:86:5
[INFO] [stdout]      |
[INFO] [stdout]   86 | /     mock! {
[INFO] [stdout]   87 | |         BMock,
[INFO] [stdout]   88 | |
[INFO] [stdout]   89 | |         self,
[INFO] [stdout] ...    |
[INFO] [stdout]   98 | |     }
[INFO] [stdout]      | |_____^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the macro `mock` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/clone.rs:43:1
[INFO] [stdout]      |
[INFO] [stdout]   43 | #[mocked(derive(Clone))]
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/clone.rs:43:1
[INFO] [stdout]      |
[INFO] [stdout]   43 | #[mocked(derive(Clone))]
[INFO] [stdout]      | ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/multi_trait.rs:126:5
[INFO] [stdout]      |
[INFO] [stdout]  126 | /     mock! {
[INFO] [stdout]  127 | |         ABMock,
[INFO] [stdout]  128 | |
[INFO] [stdout]  129 | |         self,
[INFO] [stdout] ...    |
[INFO] [stdout]  138 | |     }
[INFO] [stdout]      | |     ^
[INFO] [stdout]      | |     |
[INFO] [stdout]      | |_____move out of value occurs here
[INFO] [stdout]      |       borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/multi_trait.rs:126:5
[INFO] [stdout]      |
[INFO] [stdout]  126 | /     mock! {
[INFO] [stdout]  127 | |         ABMock,
[INFO] [stdout]  128 | |
[INFO] [stdout]  129 | |         self,
[INFO] [stdout] ...    |
[INFO] [stdout]  138 | |     }
[INFO] [stdout]      | |_____^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the macro `mock` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "associated_types") due to 2 previous errors
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/async.rs:6:5
[INFO] [stdout]      |
[INFO] [stdout]    6 |     #[mocked(TraitMock)]
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |     |
[INFO] [stdout]      |     move out of value occurs here
[INFO] [stdout]      |     borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/async.rs:6:5
[INFO] [stdout]      |
[INFO] [stdout]    6 |     #[mocked(TraitMock)]
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/multi_trait.rs:171:5
[INFO] [stdout]      |
[INFO] [stdout]  171 | /     mock! {
[INFO] [stdout]  172 | |         BMock,
[INFO] [stdout]  173 | |
[INFO] [stdout]  174 | |         self,
[INFO] [stdout] ...    |
[INFO] [stdout]  183 | |     }
[INFO] [stdout]      | |     ^
[INFO] [stdout]      | |     |
[INFO] [stdout]      | |_____move out of value occurs here
[INFO] [stdout]      |       borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/multi_trait.rs:171:5
[INFO] [stdout]      |
[INFO] [stdout]  171 | /     mock! {
[INFO] [stdout]  172 | |         BMock,
[INFO] [stdout]  173 | |
[INFO] [stdout]  174 | |         self,
[INFO] [stdout] ...    |
[INFO] [stdout]  183 | |     }
[INFO] [stdout]      | |_____^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the macro `mock` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "clone") due to 7 previous errors
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/generic_trait.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/generic_trait.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "nested") due to 1 previous error
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/cardinality.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/cardinality.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "multi_trait") due to 7 previous errors
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "cardinality") due to 1 previous error
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/generic_trait.rs:19:1
[INFO] [stdout]      |
[INFO] [stdout]   19 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/generic_trait.rs:19:1
[INFO] [stdout]      |
[INFO] [stdout]   19 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/expect_in_action.rs:5:1
[INFO] [stdout]      |
[INFO] [stdout]    5 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/expect_in_action.rs:5:1
[INFO] [stdout]      |
[INFO] [stdout]    5 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/expect_in_action.rs:11:1
[INFO] [stdout]      |
[INFO] [stdout]   11 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/expect_in_action.rs:11:1
[INFO] [stdout]      |
[INFO] [stdout]   11 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/matchers.rs:8:1
[INFO] [stdout]      |
[INFO] [stdout]    8 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/matchers.rs:8:1
[INFO] [stdout]      |
[INFO] [stdout]    8 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/type_names.rs:11:1
[INFO] [stdout]      |
[INFO] [stdout]   11 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/type_names.rs:11:1
[INFO] [stdout]      |
[INFO] [stdout]   11 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "generic_trait") due to 2 previous errors
[INFO] [stdout] warning: impl trait in impl method signature does not match trait method signature
[INFO] [stdout]   --> tests/impl_trait.rs:23:30
[INFO] [stdout]    |
[INFO] [stdout] 23 |         #[mocked(return_type=u32)]
[INFO] [stdout]    |                              ^^^
[INFO] [stdout] 24 |         fn foo(&self) -> impl Sized;
[INFO] [stdout]    |                          ---------- return type from trait method defined here
[INFO] [stdout]    |
[INFO] [stdout]    = note: add `#[allow(refining_impl_trait)]` if it is intended for this to be part of the public API of this crate
[INFO] [stdout]    = note: we are soliciting feedback, see issue #121718 <https://github.com/rust-lang/rust/issues/121718> for more information
[INFO] [stdout]    = note: `#[warn(refining_impl_trait_internal)]` (part of `#[warn(refining_impl_trait)]`) on by default
[INFO] [stdout] help: replace the return type so that it matches the trait
[INFO] [stdout]    |
[INFO] [stdout] 23 -         #[mocked(return_type=u32)]
[INFO] [stdout] 23 +         #[mocked(return_type=impl Sized)]
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "expect_in_action") due to 2 previous errors
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "async") due to 1 previous error
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/matchers.rs:8:1
[INFO] [stdout]      |
[INFO] [stdout]    8 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/matchers.rs:8:1
[INFO] [stdout]      |
[INFO] [stdout]    8 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/fn_mut_reaction.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/fn_mut_reaction.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/fn_mut_reaction.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/fn_mut_reaction.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/fn_mut_reaction.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/fn_mut_reaction.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Arg1, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1127 |     define_verify!(verify2 { (0, arg0, Arg0), (1, arg1, Arg1) });
[INFO] [stdout]      |     ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/fn_mut_reaction.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/fn_mut_reaction.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Arg1, Arg2, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1128 |     define_verify!(verify3 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2) });
[INFO] [stdout]      |     ----------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/fn_mut_reaction.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/fn_mut_reaction.rs:6:1
[INFO] [stdout]      |
[INFO] [stdout]    6 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Arg1, Arg2, Arg3, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1129 |     define_verify!(verify4 { (0, arg0, Arg0), (1, arg1, Arg1), (2, arg2, Arg2), (3, arg3, Arg3) });
[INFO] [stdout]      |     ---------------------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "type_names") due to 1 previous error
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/arbitrary_self.rs:8:1
[INFO] [stdout]      |
[INFO] [stdout]    8 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/arbitrary_self.rs:8:1
[INFO] [stdout]      |
[INFO] [stdout]    8 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/matchers.rs:366:1
[INFO] [stdout]      |
[INFO] [stdout]  366 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/matchers.rs:366:1
[INFO] [stdout]      |
[INFO] [stdout]  366 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "fn_mut_reaction") due to 5 previous errors
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/impl_trait.rs:7:5
[INFO] [stdout]      |
[INFO] [stdout]    7 |     #[mocked(TraitMock)]
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |     |
[INFO] [stdout]      |     move out of value occurs here
[INFO] [stdout]      |     borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/impl_trait.rs:7:5
[INFO] [stdout]      |
[INFO] [stdout]    7 |     #[mocked(TraitMock)]
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/matchers.rs:443:1
[INFO] [stdout]      |
[INFO] [stdout]  443 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout]      | |
[INFO] [stdout]      | move out of value occurs here
[INFO] [stdout]      | borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/matchers.rs:443:1
[INFO] [stdout]      |
[INFO] [stdout]  443 | #[mocked]
[INFO] [stdout]      | ^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Arg0, Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1126 |     define_verify!(verify1 { (0, arg0, Arg0) });
[INFO] [stdout]      |     ------------------------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of value because it is borrowed
[INFO] [stdout]     --> tests/impl_trait.rs:21:5
[INFO] [stdout]      |
[INFO] [stdout]   21 |     #[mocked(TraitMock)]
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |     |
[INFO] [stdout]      |     move out of value occurs here
[INFO] [stdout]      |     borrow of value occurs here
[INFO] [stdout]      |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]     --> tests/impl_trait.rs:21:5
[INFO] [stdout]      |
[INFO] [stdout]   21 |     #[mocked(TraitMock)]
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: if you can modify this crate, add a precise capturing bound to avoid overcapturing: `+ use<Res>`
[INFO] [stdout]     --> src/lib.rs:1097:14
[INFO] [stdout]      |
[INFO] [stdout] 1097 |         ) -> impl FnOnce() -> Res {
[INFO] [stdout]      |              ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 1125 |     define_verify!(verify0 { });
[INFO] [stdout]      |     --------------------------- in this macro invocation
[INFO] [stdout]      = note: this error originates in the attribute macro `mocked` which comes from the expansion of the macro `define_verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `mockers` (test "arbitrary_self") due to 1 previous error
[INFO] [stderr] error: could not compile `mockers` (test "matchers") due to 4 previous errors
[INFO] [stderr] error: could not compile `mockers` (test "impl_trait") due to 2 previous errors; 1 warning emitted
[INFO] running `Command { std: "docker" "inspect" "27636d7642f2e9e2ebab7480526eae27b61d05173667e39b834b645e35f41b71", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "27636d7642f2e9e2ebab7480526eae27b61d05173667e39b834b645e35f41b71", kill_on_drop: false }`
[INFO] [stdout] 27636d7642f2e9e2ebab7480526eae27b61d05173667e39b834b645e35f41b71
